home *** CD-ROM | disk | FTP | other *** search
/ IRIX Base Documentation 1998 November / IRIX 6.5.2 Base Documentation November 1998.img / usr / share / catman / p_man / cat3 / Xm / XmeGetDirection.z / XmeGetDirection
Text File  |  1998-10-30  |  7KB  |  133 lines
  1.  
  2.  
  3.  
  4.      XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn((((3333XXXX))))       UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV       XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn((((3333XXXX))))
  5.  
  6.  
  7.  
  8.      NNNNAAAAMMMMEEEE
  9.           XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn - A compound string parse procedure to
  10.           insert a direction component
  11.  
  12.      SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
  13.           #include <Xm/XmP.h>
  14.           XXXXmmmmIIIInnnncccclllluuuuddddeeeeSSSSttttaaaattttuuuussss XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn(
  15.           XXXXttttPPPPooooiiiinnnntttteeeerrrr ****tttteeeexxxxtttt____iiiinnnn____oooouuuutttt,
  16.           XXXXttttPPPPooooiiiinnnntttteeeerrrr tttteeeexxxxtttt____eeeennnndddd,
  17.           XXXXmmmmTTTTeeeexxxxttttTTTTyyyyppppeeee ttttyyyyppppeeee,
  18.           XXXXmmmmSSSSttttrrrriiiinnnnggggTTTTaaaagggg ttttaaaagggg,
  19.           XXXXmmmmPPPPaaaarrrrsssseeeeMMMMaaaappppppppiiiinnnngggg eeeennnnttttrrrryyyy,
  20.           iiiinnnntttt ppppaaaatttttttteeeerrrrnnnn____lllleeeennnnggggtttthhhh,
  21.           XXXXmmmmSSSSttttrrrriiiinnnngggg ****ssssttttrrrr____iiiinnnncccclllluuuuddddeeee,
  22.           XXXXttttPPPPooooiiiinnnntttteeeerrrr ccccaaaallllllll____ddddaaaattttaaaa);
  23.  
  24.      VVVVEEEERRRRSSSSIIIIOOOONNNN
  25.           This page documents Motif 2.1.
  26.  
  27.      DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
  28.           XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn is a compound string parse procedure (a
  29.           function of type XXXXmmmmPPPPaaaarrrrsssseeeePPPPrrrroooocccc).  It is suitable for use as an
  30.           XXXXmmmmNNNNiiiinnnnvvvvooookkkkeeeePPPPaaaarrrrsssseeeePPPPrrrroooocccc procedure in an XXXXmmmmPPPPaaaarrrrsssseeeeMMMMaaaappppppppiiiinnnngggg data type.
  31.  
  32.           XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn is triggered when the implicit direction of
  33.           the current character in text being parsed is different from
  34.           the direction of the previous character.  The function
  35.           assumes that _t_e_x_t__i_n__o_u_t points to the character whose
  36.           direction has changed.  It creates a compound string with a
  37.           component of type XXXXmmmmSSSSTTTTRRRRIIIINNNNGGGG____CCCCOOOOMMMMPPPPOOOONNNNEEEENNNNTTTT____DDDDIIIIRRRREEEECCCCTTTTIIIIOOOONNNN that
  38.           specifies the direction of the character at the _t_e_x_t__i_n__o_u_t
  39.           position.  The argument _t_e_x_t__i_n__o_u_t remains unchanged.
  40.  
  41.           _t_e_x_t__i_n__o_u_t
  42.                     Specifies the text being parsed.  The value is a
  43.                     pointer to the first byte of a character whose
  44.                     implicit direction is different from that of the
  45.                     previous character.  When the parse procedure
  46.                     returns, this argument is not set to a value
  47.                     different from the input value.
  48.  
  49.           _t_e_x_t__e_n_d  Specifies a pointer to the end of the _t_e_x_t__i_n__o_u_t
  50.                     string.  If _t_e_x_t__e_n_d is _N_U_L_L, the string is
  51.                     scanned until a _N_U_L_L character is found.
  52.                     Otherwise, the string is scanned up to, but not
  53.                     including, the character whose address is
  54.                     _t_e_x_t__e_n_d.
  55.  
  56.           _t_y_p_e      Specifies the type of text and the tag type.  For
  57.                     locale text, _t_y_p_e has a value of either
  58.                     XXXXmmmmMMMMUUUULLLLTTTTIIIIBBBBYYYYTTTTEEEE____TTTTEEEEXXXXTTTTor XXXXmmmmWWWWIIIIDDDDEEEECCCCHHHHAAAARRRR____TTTTEEEEXXXXTTTT.  For charset
  59.                     text, _t_y_p_e has a value of XXXXmmmmCCCCHHHHAAAARRRRSSSSEEEETTTT____TTTTEEEEXXXXTTTT.
  60.  
  61.  
  62.  
  63.      Page 1                                         (printed 10/24/98)
  64.  
  65.  
  66.  
  67.  
  68.  
  69.  
  70.      XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn((((3333XXXX))))       UUUUNNNNIIIIXXXX SSSSyyyysssstttteeeemmmm VVVV       XXXXmmmmeeeeGGGGeeeettttDDDDiiiirrrreeeeccccttttiiiioooonnnn((((3333XXXX))))
  71.  
  72.  
  73.  
  74.           _t_a_g       Specifies the tag to be used in determining the
  75.                     character direction.
  76.  
  77.           _e_n_t_r_y     Specifies the parse mapping that triggered the
  78.                     call to the parse procedure.
  79.  
  80.           _p_a_t_t_e_r_n__l_e_n_g_t_h
  81.                     Specifies the number of bytes in the input text
  82.                     that constitute the matched pattern.
  83.  
  84.           _s_t_r__i_n_c_l_u_d_e
  85.                     Specifies a pointer to a compound string.  The
  86.                     parse procedure creates a compound string to be
  87.                     included in the compound string being constructed.
  88.                     The parse procedure then returns the compound
  89.                     string in this argument.
  90.  
  91.           _c_a_l_l__d_a_t_a Specifies data passed by the application to the
  92.                     parsing routine.
  93.  
  94.      RRRREEEETTTTUUUURRRRNNNN
  95.           This function returns XXXXmmmmIIIINNNNSSSSEEEERRRRTTTT, indicating that the parsing
  96.           routine should concatenate the result to the compound string
  97.           being constructed and continue parsing.
  98.  
  99.      RRRREEEELLLLAAAATTTTEEEEDDDD
  100.           XXXXmmmmPPPPaaaarrrrsssseeeeMMMMaaaappppppppiiiinnnngggg(3), XXXXmmmmPPPPaaaarrrrsssseeeeTTTTaaaabbbblllleeee(3), XXXXmmmmSSSSttttrrrriiiinnnngggg(3), and
  101.           XXXXmmmmeeeeGGGGeeeettttNNNNeeeexxxxttttCCCChhhhaaaarrrraaaacccctttteeeerrrr(3).
  102.  
  103.  
  104.  
  105.  
  106.  
  107.  
  108.  
  109.  
  110.  
  111.  
  112.  
  113.  
  114.  
  115.  
  116.  
  117.  
  118.  
  119.  
  120.  
  121.  
  122.  
  123.  
  124.  
  125.  
  126.  
  127.  
  128.  
  129.      Page 2                                         (printed 10/24/98)
  130.  
  131.  
  132.  
  133.